Please address the comments from this code review:

## Overall Comments
- The 60-second retry delay is hard-coded in multiple places (WINDOW_RETRY_DELAY_MS and i18n messages); consider centralizing this as a single constant or configurable setting to avoid drift if the delay is ever changed.
- When auto-launching the game with `maaService.runAction(path, '', basePath, false)`, you might want to validate that `gamePath` points to an existing and executable file before attempting to run it, so that misconfigurations fail fast with a clearer message.

## Individual Comments

### Comment 1
<location> `src/stores/appStore.ts:1286` </location>
<code_context>
     },

+    // 游戏路径设置（窗口未找到时自动启动游戏）
+    gamePath: '',
+    setGamePath: (path) => set({ gamePath: path }),
+
</code_context>

<issue_to_address>
**issue (bug_risk):** The second `gamePath` initialization overwrites the value loaded from config, breaking persistence.

This `gamePath: ''` definition in the store’s initial state will override the earlier `config.settings.gamePath ?? ''` initialization, so any persisted path from config is discarded on startup. Please remove this initializer (and rely on `setGamePath`) or otherwise ensure the config-derived value is not overwritten.
</issue_to_address>

### Comment 2
<location> `src/components/Toolbar.tsx:486-489` </location>
<code_context>
+            }
+
+            log.info(`实例 ${targetInstance.name}: 未找到窗口，尝试启动游戏: ${path}`);
+            addLog(targetId, {
+              type: 'info',
+              message: t('action.autoLaunchGameStarting', { path }),
+            });
+
+            try {
+              await maaService.runAction(path, '', basePath, false);
+            } catch (launchErr) {
+              log.error(`实例 ${targetInstance.name}: 启动游戏失败:`, launchErr);
+              addLog(targetId, {
+                type: 'error',
+                message: t('action.autoLaunchGameFailed', { error: String(launchErr) }),
+              });
+              return false;
+            }
+
+            addLog(targetId, {
+              type: 'info',
+              message: t('action.autoLaunchGameWaiting', { seconds: 60 }),
+            });
+            await new Promise((resolve) => setTimeout(resolve, WINDOW_RETRY_DELAY_MS));
</code_context>

<issue_to_address>
**suggestion:** The hardcoded `60` seconds in the log can drift from `WINDOW_RETRY_DELAY_MS`.

Since `WINDOW_RETRY_DELAY_MS` is `60_000`, this log should derive the seconds from that constant (e.g. `WINDOW_RETRY_DELAY_MS / 1000`) so the message stays accurate if the delay changes.

```suggestion
            addLog(targetId, {
              type: 'info',
              message: t('action.autoLaunchGameWaiting', { seconds: WINDOW_RETRY_DELAY_MS / 1000 }),
            });
```
</issue_to_address>